home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Aminet 28
/
Aminet 28 (1998)(GTI - Schatztruhe)[!][Dec 1998].iso
/
Aminet
/
dev
/
lang
/
nrcobol_1e.lha
/
NRCOBOL1e
/
NRCOBOL.readme
< prev
next >
Wrap
Text File
|
1998-09-22
|
25KB
|
669 lines
NRcobol Version 1.0e by cHArRiOTt September 98
1.Introduction
2.Installation
3.Usage
4.Syntax
5.Implemented?
6.History
7.Todo
8.Bugs
9.Feedback
10.Contacts
11.Distribution
12.Credits
13.Disclimer
14.Apologies
15.Thanks
16.finally
NUff REsPEct.....peace n more time.
-------------------------------------------------------------------------
1.Introduction ...Why COBOL?
To those of you thinking not another new language, COBOL is in fact one
of the oldest high-level languages, its roots going back to the late
1950's. Ofcourse there are those of you who already know this but regard
COBOL as not so much an high-level language, as the original computer
virus. To these people i say RESPECT the source of the mother tounge. (sic!)
When so many languages have come and gone (what ever happended to
Modulus II, and who outside of the Amiga community has heard of 'E;), COBOL
(with the most source code on the planet, circa 89) has seen in the advent
of STRUCTURED,and now OBJECT methodologies, its adapted absorbing the latest
in Database Management, SQL etcetera, and gone on from strength to strength.
Indeed as an introduction to records there's alot to be said in its favour.
So when people say why, i say why not?
This implementation of COBOL is largely ANSI 85 compatable and takes the
form of MicroSoft(TM) COBOL, with maybe the exception of some stuff in
ENVIRONMENT DIVISION - SPECIAL-NAMES. And some stuff left over from the days
when memory was premium and no one had the imagination to contemplate speed.
see Implementation?
This would have been bought to you sooner, if it weren't for the moron, in
the bedsit down stairs, with something of an habit!! which in lean times
even extend to a fixation with gas. 'would you adam n eve it'.
WARNING dope really @&*$% you up! something to do with short term memory
going to pot!
STOP THE PRESS!.
"COMPUTING" MAY 8th 97
'Cobol crisis looms' The skills cris is luring Cobol programmers out of
retirement with offers of up to £1000 ($1700) per day...... hmm :-)
-------------------------------------------------------------------------
2.Installation
Nothing could be simpiler, Just copy the runtime program 'RUNCOB' anywhere
in your path, that's ram: c: or in the same directory as the created .INT
files.
Files with the extension .INT are created as a result of successfully
running NRCOBOL ..see Usage
There are several ToolTypes which you'll need to tailor to suite your
system. To access these single click on the icon of NRCOBOL, then select
information from the sysem menu to find the following:
TEXTEDITOR=C:ed
edit cobol source file.
TEXTVIEWER=sys:utilities/multiview
view list / debug files, if not set then the editor set for TEXTEDITOR
is used.
SOURCEDIR=
where cobol source files are to found by NRCOBOL's requester
RUNCOBDIR=
where runcob prog is to be found, default ram: c: or current directory
Note: the absence of a space after the '=' and in the case of SOURCEDIR
and RUNCOBDIR if a directory is stated it should end with ':' or '/'
To avoid those moments of head scratching, you are advised to use ABSOLUTE
path names. see.. 15.Thanks
If you are one the few who haven't yet discovered 'UrouHack' by Tinic Urou
then i urge you to get hold of a copy aminet util/wb. This prog redefines
the system gadgets to very impressive xen like gadgets and leaves the rest
of the system looking like MUI, and then some, without slowing the system
down. If that's not reason enough, it also improves the appearence of this
prog :)
-------------------------------------------------------------------------
3.Usage
After creating your cobol source file with your favourite text editor,
and saving it with the .COB extention you have a choise of evoking the
compiler from CLI/shell or Workbench.
From CLI/SHELL
NRCOBOL <sourcefile>.(COB | CBL) [-l] [-d] [-e]
where the optional flags:
-l produces a simple listing <sourcefile>.LST
-d produces a debug listing <sourcefile>.DBG
-e errors ignored when compiling with wildcard option
The wildcard pattern match option will now recognize #?.(cob|cbl)
A successfull compilation produces <sourcefile>.INT
to run type... RUNCOB <sourcefile>.INT
From Workbench
Use of the program from workbench is self explanatory, but for those
too dim.
+-----------------------------------------------+
| [.][#]
|+--------------------------------------------+-|
||Titles || | <-- What When Who
|| || |
|| || |
|+-------------------------------------------+| |
|File: | || | <-- current sourcefile.COB
| +-------------------------------------+| |
|____________________________________________ | |
|| || |
|| IDENTIFICATION * || | <-- status block
|| ENVIRONMENT * || | *'s replaced by
|| DATA * || | PASSED or FAILED
|| PROCEDURE * || |
|| || |
|| || | <-- current line
|+-------------------------------------------+| |
|+--------+ +-+ +---+ +--+ +------+| | <-- ancillary output files
|| | | | List +---+ Debug +--+ | || | as .LST and/or .DBG
||COMPILE | |>| +--------+ +--------+ |EDITOR|| |
|| | | | | ABORT | | RUN! | | ||_|
|+--------+ +-+ +--------+ +--------+ +------+|=|
+---------------------------------------------+-+
^ ^ ^
| | |
| | Edit sourcefile.COB/LST/DBG
| filerequester
Make it so #1
The Editor option allows one to view sourcefile.COB, sourcefile.LST or
sourcefile.DBG. The file editor defaults to 'ED' as supplied in sys:c.
You can however, set TEXTEDITOR in NRcobol's icon to launch your favourite
editor. eg TEXTEDITOR=c:ced . Note no space between = and editor named.
see.. 2.Installation
The menu options allow:
1, A window on a custom screen, ie high resolution non interlace or
a window on the current public screen.
2, The date check on debug/listing files can to be disabled,
ie, open the last debug/listing file related to current cobol source file,
regardless of the date on the source file.
3, Terminal runtime check on SIZE ERROR condition.
For those of you looking to automate compilation, possibly using
Arexx, the following codes are now returned by NRCOBOL:
8000 nrcobol ? called
8001 filename error
8002 compilation error
8003 savefile error (.int or T:debug_) file
8004 identifier limits
8005 too many files found with wildcard. [500 max]
1002 memory error
In both cases an ICON is produced named <sourcefile>.INT
to execute just double click.
The debug option produces a file which you may find useful in locating
runtime errors, which sadly is normal for cobol. Usually this is to do with
uninitialised variables, you know, finding alpha data in a numeric field.
Runtime errors usually return a value in the form 0x????, where 0x???? is an
offset into the data space allocated in the Data Division. Stradling values,
ie value between offset values indicates a postion within a table,
(a subsripted identifier).
-------------------------------------------------------------------------
4.Syntax
I may at a later date add the syntax, in the mean time the following
books are recomended:
- COBOL for the IBM Personal Computer by kip R Irvine
- COBOL for the 80's by J Wayne Spence
- Structur